122

A. Banerjee et al.

It is by and large perceived that for a character framework to act naturally

sovereign, clients control the unquestionable certifications that they hold, and their

nod is needed to utilize those credentials. This decreases the unintended sharing of

clients’ very own information.

In the SSI framework, holders produce and control exceptional identifiers called

decentralized identifiers. Most SSI frameworks are decentralized, where the certi-

fications are confirmed utilizing public-key cryptography secured on a circulated

ledger.

3.3

Hyperledger Indy

Hyperledger Indy is an initiative for Decentralized Identity Management. Hyper-

ledger Indy gives tools, libraries, and reusable segments for giving computerized

self-sovereign personalities established on blockchains or other disseminated records

so they are interoperable across managerial spaces and applications. Initially, the

Hyperledger Indy Codebase was built by Evernym. It was then donated to the Sovrin

Foundation, which implemented a practical hosted ledger of identity. Indy was even-

tually donated and hosted at Hyperledger where it currently sits in an active status

and is one of the many projects to have crossed the incubation stage at the time of

writing. The advantage of using Hyperledger Indy is as follows:

a.

Users have full control over their identities.

b.

Other third parties need permission from the user.

c.

Users can utilize their identities on any network, which allows them.

d.

Users can wipe out or update ID.

e.

The user is independent on the decentralized platform.

f.

Disclosure of any documentation is limited.

In the following sections, we discuss Hyperledger Indy in detail. This is not

supposed to be a full hand-on primer but rather an overview of essential concepts,

which are key to developing solutions using Hyperledger Indy. For this, we propose

a hypothetical network of Internet of Things Drone Network, which can be used

for Surveillance. We discuss the core concepts and procedures of Hyperledger Indy

using this network, which we shall, from here on out, refer to as Network D (for

“Drones”). The Ledger maintained by this network D is public, and permissioned

meaning anyone can view the Drones part of the network and the transactions but

not commit/write to the ledger in any fashion.

Section 3.3.1 discusses core concepts of Hyperledger Indy, Sect. 3.3.2 gives the

onboarding process for a drone [31] (entry into the network), Sect. 3.3.3 outlines

revocation of entry, and Sect. 3.3.4 gives active use cases of Hyperledger Indy.